Reducing latency

ABSTRACT

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for reducing latency in network communications and data presentation. In one aspect, a user session is initiated in which data related to an account is presented to the user. A user group to which the given user has been assigned is identified. A first dataset related to the account is selected based on the user group. A second dataset related to the account is selected based on types of data previously requested by various other users in the user group. A user interface for the account is updated to present at least a portion of the first dataset. Latency in updating the user interface is reduced when presenting additional portions of the first dataset or the second dataset by providing, to the client device, the second dataset prior to receiving a request for the second dataset.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of, and claims priorityto, U.S. patent application Ser. No. 15/378,583, titled “REDUCINGLATENCY,” filed on Dec. 14, 2016, which is a continuation of U.S. patentapplication Ser. No. 15/005,788, titled “REDUCING LATENCY,” filed onJan. 25, 2016. The disclosure of the foregoing application isincorporated herein by reference in its entirety for all purposes.

BACKGROUND

The Internet facilitates the exchange of information and transactionsbetween users across the globe. This exchange of information enablesdata providers to provide data to a variety of users. Data may beprovided in response to multiple requests received from a client device.However, each request requires the use of computing resources (e.g.,servers and memory storage devices) and network resources (e.g.,routers, switches, and network bandwidth) to respond with the requesteddata. In addition, each request takes some time for a data provider toidentify the appropriate data and send the data over the network to theclient device.

SUMMARY

This specification describes technologies relating to reducing latencyin network communications and in data presentation.

In general, one innovative aspect of the subject matter described inthis specification can be embodied in methods that include the actionsof authenticating a given user as an authorized user of a given onlineaccount based on data submitted through a client device of the givenuser; initiating, for the given user and in response to theauthenticating, a user session in which data related to an account ispresented to the user, the account being accessible by multiple usershaving credentials to access the account; identifying a user group towhich the given user has been assigned based on (i) similarities betweenthe given user's interactions with user interface elements presented inthe user interface of the account during previous user sessions andother interactions of other users with the user interface elements or(ii) similarities between at least one type of data requested by thegiven user during the previous user sessions and at least one type ofdata requested by other users; selecting, based on the user group towhich the given user has been assigned, a first dataset related to theaccount, the first dataset being selected based at least on (i) thetypes of data requested by the given user during the previous usersessions and (ii) user interface elements with which the given user hasinteracted during previous user sessions; selecting, based on types ofdata previously requested by various other users in the user group, asecond dataset related to the account; updating a user interface for theaccount to present at least a portion of the first dataset in an initialaccount view for the account, the initial account view presentingmultiple different types of data combined into a single presentation andthat provides an overview of the account; and reducing latency inupdating the user interface for the account when presenting additionalportions of the first dataset or the second dataset at the client deviceby providing, to the client device, the second dataset prior toreceiving a request for the second dataset from the client device, wherethe second dataset is cached at the client device and is not presentedin the initial account view. Other embodiments of this aspect includecorresponding systems, apparatus, and computer programs, configured toperform the actions of the methods, encoded on computer storage devices.

These and other embodiments can each optionally include one or more ofthe following features. In some aspects, the given user and the otherusers can be assigned to the user group using a machine learning processthat creates multiple user groups and assigns users to the multiple usergroups. In some aspects, the given user can be assigned to the usergroup based additionally on at least one of (i) a time range of datarequested by the given user in a previous user session, (ii) datamodified by the user, or (iii) a frequency with which the given useraccesses data related to the account.

In some aspects, at least a portion of the second dataset can beselected based on at least one of (i) types of data requested by thegiven user in the previous user sessions, (ii) a time range of datarequested by the given user in a previous user session, or (iii) ageographic region from which the given user has requested data in theprevious user sessions. In some aspects, each of the multiple users isprovided a different initial account view based on types of datarequested by each of the multiple different users.

Some aspects can include updating, for each given user session initiatedfor the given user, a user profile for the given user with data thatspecifies user interface elements with which the given user interactedduring the given user session and types of data that the given usersrequested during the user session and modifying the initial account viewfor the given user based on the updating.

Some aspects can include determining to update the cache of second dataat the user device based on a data cost for updating the cache beingless than a threshold cost and providing, to the user device, an updateddataset in response to determining to update the cache. Some aspects caninclude identifying two or more campaigns of the account that have atleast one same characteristic and at least one characteristic thatdiffers for each of the two or more campaigns and providing data thatpresents data of each of the two or more campaigns and in a manner thathighlights the at least one characteristic of each of the two or morecampaigns.

Particular embodiments of the subject matter described in thisspecification can be implemented so as to realize one or more of thefollowing advantages. The latency in presenting data to a user can bereduced by pre-caching, at the user's device, data that the user islikely to request but has not yet requested. By pre-caching the data,the number of requests submitted over a network, and thus the amount ofdemand placed upon network and computing resources used to respond tothe requests, can be reduced. This reduction in demand placed upon thenetwork and computing resources can improve the performance of thenetwork and computing resources by increasing the speed at which theresources respond to the requests and minimizing errors and performancedegradation caused by overloading the resources. The demand placed uponcomputing resources is also reduced by retrieving requested data andadditional data for pre-caching at the same time rather than querying adata source multiple times.

Pre-caching data that a user is likely to request also allows the clientdevice to present the requested data quicker as the client device doesnot have to wait for a request to traverse the network, the server toidentify the requested data, and the requested data to make its way tothe client device. In addition, user frustration is reduced bypresenting data without network in response to requests submitted by theuser. The demand placed upon the network and computing resources can bealso be reduced by selectively determining when to update the datastored in the cache.

The details of one or more embodiments of the subject matter describedin this specification are set forth in the accompanying drawings and thedescription below. Other features, aspects, and advantages of thesubject matter will become apparent from the description, the drawings,and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an example environment in which a pre-caching system providesdata for caching at a client device.

FIG. 2 is an example environment in which an account management systemmanages account data and provides user interfaces that present theaccount data.

FIG. 3 is a screenshot of an example user interface in which accountdata is presented.

FIG. 4 is a flow chart of an example process for reducing latency inpresenting account data.

FIG. 5 is a flow chart of an example process for updating a cache.

FIG. 6 is a flow chart of an example process for assigning a given userto a user group and identifying data to provide to the given user basedon the user group.

FIG. 7 is a flow chart of an example process for generating avisualization that presents account data for multiple campaigns.

Like reference numbers and designations in the various drawings indicatelike elements.

DETAILED DESCRIPTION

A system can reduce latency in presenting data by sending data to aclient device and caching the data at the client device prior to theclient device submitting a request for the data. However, the amount ofdata that can be cached is generally smaller than the amount ofavailable data. As such, the system must determine which data to cachefor different users so that the benefits provided by caching data (e.g.,faster user interface updates and/or real time interactions with theuser interface) can be realized. The system can select data to provideto a client device based on a user's previous interactions with a userinterface that presents the data. For example, if a user has requestedparticular data for a particular time period multiple times (e.g., datafor the previous week), the system may provide the particular data forthat time period prior to the user actually submitting a request for thedata. If the user later submits a request for the data, the data iscached at the user device and can be obtained and presented more quicklythan if the client device had to request the data from a remote system,e.g., over a network. Additional data can also be cached by the remotesystem for faster delivery to the client device.

The system can send data for presentation to a user and data for cachingat the user's device when the user accesses an account managed by thesystem. For example, when a user logs into their account, the system canprovide a user interface that includes an initial account view within adashboard and additional data for caching at the user's device. Thedashboard can include an overview of the account that includes a summaryof data selected for the user based on the user's previous interactionswith user interfaces provided by the system. The manner in which thedata is presented can also be selected based on the user's previousinteractions with user interfaces provided by the system. These userinteractions can include, for example, particular user interfaceelements (e.g., controls, display cards, etc.) that the user has viewed,selected, or with which the user has interacted, types of data requestedby or modified by the user, and/or dimensions of data (e.g., data withina particular time period or related to a particular geographiclocation). The user can then interact with user interface elements ofthe dashboard to view different data or view different types ofpresentations of the data. In response, the appropriate data can beobtained from the cached data or requested from the system thatmaintains the data.

The data presented in the initial account view and/or the data providedfor caching at the client device can be selected based on a user groupto which the user is assigned. For example, certain groups of users mayrequest similar types of data and/or interact with similar types of userinterface elements. In a particular example, users that have similarroles but in different organizations (e.g., brand managers) may requestand view similar types of data and data within similar dimensions. Insome implementations, the data that is cached for a given user can beselected based on actions performed by other users in the group evenwhen the given user has not performed those actions.

FIG. 1 is an example environment 100 in which a pre-caching system 110provides data for caching at a client device 130. The pre-caching system110 can provide data from a data storage device 115 in response to datarequests 140 received from the client device 130. The client device 130provides the data requests 140 over a data communication network 120,e.g., a local area network (LAN), a wide area network (WAN), theInternet, or a combination thereof. Each data request 140 can specifyparticular data that a user has requested using the client device 130.

In response to each data request 140, the pre-caching system 110 canobtain the requested data from the data storage device 115 and providethe requested data 142 to the client device 130. For example, thepre-caching system 110 may send to the client device 130 the requesteddata 142 in one or more transmissions of one or more data packets. Thepre-caching system 110 can also select and provide additional data 144that was not requested by the data request 140. For example, the user ofthe client device 130 may not have requested the additional data 144.The additional data 144 can be cached at the client device 130 so thatthe additional data 144 can be provided quickly and without submittinganother data request over the network 120 if the user requests theadditional data 144. For example, the additional data 144 can be storedin a high-speed cache 135 of the client device 130. The high-speed cache135 can include high-speed memory devices installed on the client device130 and that store the additional data 144.

In some implementations, the pre-caching system 110 selects theadditional data 144 based on a user of the client device 130. Forexample, the pre-caching system 110 may select the additional data 144based on the user's previous interactions with one or more userinterfaces that present data to the user, e.g., one or more userinterfaces provided by the pre-caching system 110. The user interactionsthat the pre-caching system 110 uses to select the additional data 144can include, for example, user interface elements (e.g., controls,display cards, types of graphs, etc.) with which the user hasinteracted, types of data requested by the user (e.g., keywords,performance measures, bids, etc.), actual data requested by the user(e.g., particular campaigns, particular keywords, particular contentitems, etc.), dimensions of data requested by the user (e.g., particulartime periods, particular geographic locations, particular value ranges,etc.), how often the user accesses the account, and/or preferencesselected by the user. For example, if a user requested during a previoususer session the previous week's impression data for a particularadvertising campaign, the pre-caching system 110 may provide asadditional data for a current user session the previous week'simpression data for the particular campaign prior to the user requestingthis data.

In some implementations, some data requests 140 may be general orimplicit requests rather than specific requests for specific data. Forexample, the pre-caching system 110 may generate and provide a userinterface, e.g., a dashboard, with an initial account view that providesan overview of an account response to a user logging into or otherwiseaccessing the account. This summary of data can be selected in responseto the user logging into the account rather than a specific request forthe data included in the overview. The pre-caching system 110 can alsoselect and provide additional data that the user may request afterviewing the dashboard.

In some implementations, the pre-caching system 110 may also cacheadditional data at the pre-caching system 110. In this way, thepre-caching system can more quickly provide the data in response to adata request that specifies the additional data. This additional datacan be selected in a similar manner as the additional data 144 sent tothe client device 130. For example, the pre-caching system 110 mayselect a set of additional data for pre-caching. The pre-caching system110 may send a subset of the additional data to the client device 130for caching at the client device. The pre-caching system 110 may alsocache a subset of the additional data at the pre-caching system 110. Forexample, the pre-caching system 110 may identify, from the set ofadditional data, data that the user is most likely to select and providethat data to the client device 130. The remaining data of the set ofadditional data may be cached at the pre-caching system 110. Thiscaching at the pre-caching system 110 can reduce latency in providingthe data to the client device 130 as obtaining the data from the datastorage device 115 in response to requests for the data can take sometime and increase the demand on computing resources used to obtain thedata.

FIG. 2 is an example environment 200 in which an account managementsystem 210 manages online account data and provides user interfaces thatpresent the account data. The account management system 210 can includeone or more servers located in one or more data centers. The one or moreservers can receive requests for online account data over a datacommunication network 250, e.g., a LAN, a WAN, the Internet, or acombination thereof. For example, the account management system 210 caninclude one or more front-end servers 240 that receives requests foronline data and provides requested data to client devices 262 and 272over the network 250. The account management system 210 can also includeone or more back-end servers that receives the requests from thefront-end server(s), obtains appropriate account data based on therequests, and provides the obtained data to the front-end server(s) 240.

The account management system 210 can manage online account data formultiple different accounts of multiple different account holders. Forexample, the account management system 210 can manage advertisingaccount data for multiple different organizations, e.g., account holders260 and 270. Although two account holders 260 and 270 are illustrated inFIG. 2, the account management system 210 can manage account data forother numbers of account holders. The systems and techniques describedbelow can also be applied to various other types of data.

The account data managed by the account management system 210 caninclude any data related to an account, such as performance data forcontent items (e.g., number of impressions, click through rates,conversion rates, etc.), budget information for account holders, and/orcontent item distribution criteria. The account data for each accountholder is stored in an account data storage device 227, which mayinclude multiple data storage devices located in one or more datacenters. The account data for each account holder may be storedseparately and securely such that account data for one account holder isnot provided to users of a different account holder.

Each account holder 260 and 270 can have one or more authorized usersthat are authorized to view data related to the account(s) of theaccount holder. For example, an organization may have multiple usersthat are authorized to manage campaigns for which the account managementsystem 210 maintains account data. Each user authorized to accessaccount data of the account holder 260 can access the account data usinga client device 262-1-262-n. Similarly, each user authorized to accessaccount data of the account holder 270 can access the account data usinga client device 272-1-272-n. The users may be prompted to inputcredentials (e.g., username and password) prior to being given access toaccount data.

A client device is an electronic device that is capable of requestingand receiving electronic resources and other data over the network 250.Example client devices include personal computers, mobile communicationdevices (e.g., smartphones, tablet computing devices, and/or smartwatches), and other devices that can send and receive data over thenetwork 250. A client device typically includes a user application, suchas a web browser, to facilitate the sending and receiving of data overthe network 250. The web browser can enable a user to interact withtext, images, videos, music, and other information typically located ona web page at a website. A client device can include other applications,e.g., native applications developed for a particular type of device orfor a particular platform.

Each client device 262 and 272 can include a high-speed cache 264 and anaccount viewer 266. The account viewer 266 is an application thatpresents account data to a user of a client device. The account viewer266 may be a web browser or a native application that requests accountdata from the account management system 210 and presents the accountdata using one or more user interfaces, as described in more detailbelow.

The high-speed cache 264 includes high-speed memory devices that storeaccount data that may be presented by the account viewer 266. Forexample, the high-speed cache 264 may include static random-accessmemory (SRAM) and/or solid state memory devices. The high-speed cache264 may store account data that has not yet been requested by a user ofthe client device. When the user requests account data stored in thehigh-speed cache 264, the account viewer 266 can obtain the account dataquickly from the high-speed cache 264 and without submitting a requestfor the account data over the network 250. This pre-caching of datareduces the latency in presenting the account data and reduces thedemand placed on the network 250 and computing resources of the accountmanagement system 210.

In some implementations, the account viewer 266 can be configured tocheck the high-speed cache 264 in response to requests for account data.If the requested account data is found in the high-speed cache 264, theaccount viewer 266 can obtain the account data from the high-speed cache264 and present the account data to the user. If the requested accountdata is not in the high-speed cache, the account viewer 266 can requestthe account data from the account management system 210, e.g., bysubmitting a request over the network 250.

The account management system 210 includes a data transmission subsystem220, an interaction logger 230, and a user group engine 235. The datatransmission subsystem 220 receives and responds to requests for accountdata. The data requests may include specific requests for specificaccount data. An example of a specific request is a request forperformance data for a particular campaign and during a particular timeperiod. The account management system 210 can also provide account datain response to general or implicit requests. An example of a general orimplicit request is a user logging into an account that the user isauthorized to access. In this example, the data transmission subsystem220 may select a summary of data to provide in an initial account viewfor the user.

The data transmission subsystem 220 includes a data selector 221 and auser interface generator 229. The data selector 221 identifies accountdata to provide in response to data requests (e.g., specific, general,or implicit requests) received from client devices. For example, thedata selector 221 may access the account data storage device 227 toobtain specific data specified by a specific data request. For generalor implicit data requests, the data selector 221 can select a subset ofthe account data based on the particular user for which the request wasmade. This subset of account data is a subset of the account data of anaccount that the user is authorized to access. For example, as describedin more detail below, the data selector 221 may select a subset of theaccount data to provide based on the user's previous interactions withuser interfaces provided by the account management system 210.

The user interface generator 229 can generate various user interfacesthat present account data. The user interfaces can include a dashboardthat includes user interface elements (e.g., controls, display cards,menus, etc.) that enable the user to request and view various data invarious formats (e.g., graphs, charts, tables, etc.). The dashboard maypresent an initial account view each time the user initially accesses anaccount, e.g., in response to the user logging into an account. Theinitial account view can include a subset of the account data, e.g.,that provides an overview of the account and that is adapted to the userthat is accessing the account. As described in more detail below, thesummary of account data can include data selected based on the user'sprevious interactions with user interfaces provided by the accountmanagement system 210.

The user interfaces can include one or more display card user interfaceelements. Each display card can present a particular type of data in aparticular way. For example, a first display card may present impressiondata for a content item in a table while a second display card maypresent click through rates for multiple keywords for distributing thecontent item using a bar graph. In some implementations, the userinterface generator 229 selects display cards to provide in the initialaccount view based on the user's previous interactions with the displaycards or other user interface elements. For example, if the user selectsto view a particular display card at least a threshold number of times,the user interface generator 229 may provide the particular display cardin the initial account view. In another example, the user interfacegenerator 229 may include in the initial account view one or moredisplay cards that the user selects to view with the greatest frequency.As described in more detail below, the user interface generator 229 mayalso select display cards for inclusion in the initial account viewbased on a user group to which the user is assigned. An example userinterface is illustrated in FIG. 3 and described below.

The interaction logger 230 logs data describing users' interactions withuser interfaces provided by the account management system 210 and/orpresented by the account viewer 266. As described in more detail below,this interaction data is used to select account data that is provided tothe user. For example, each user may log into their account to viewaccount data and/or make changes to the accounts to which the user isauthorized to view and makes changes. While the user is logged in, andwith the user's permission, the interaction logger 230 can receive datadescribing the user's interactions with the user interfaces and storethe data in a secure interaction log 232. For example, the accountviewer 266 may include embedded scripts that obtain the data for eachinteraction and provides the data to the interaction logger 230. Thedata describing a user's interactions stored in the interaction log 232can include, for example user interface elements (e.g., controls,display cards, types of graphs, etc.) with which the user hasinteracted, types of data requested by the user (e.g., keywords,performance measures, bids, etc.), actual data requested by the user(e.g., particular campaigns, particular keywords, particular contentitems, etc.), dimensions of data requested by the user (e.g., particulartime periods, particular geographic locations, particular value ranges,etc.), how often the user accesses the account, preferences selected bythe user, and/or other appropriate interaction data.

In some implementations, the interaction logger 230 generates a userprofile for each user that includes the logged data. In the user profilefor a user, the interaction logger 230 may include data identifying eachuser interface element with which the user has interacted, the number oftimes the user has interacted with the user interface element, and/orthe frequency with which the user has interacted with the user interfaceelement. The user profile for a user may also include data identifyingeach type of data requested by the user, a number of times the user hasrequested each type of data, and a frequency with which the userrequests each type of data. The same identifying and frequency data canbe stored for each particular portion of actual data requested by theuser. For each type of data and/or for each particular portion of datarequested by the user, the user profile can include the dimensions forthe data. For example, if the user requested the performance of aparticular content item during a particular time period, the userprofile will include data specifying the particular time period for thattype of data (performance data) and for the actual data (performance ofthe particular content item). After each user session in which the useraccesses the online account, the user interaction logger 230 can updatethe user's profile to describe the user's interactions with data anduser interface elements during the user session.

The user group engine 235 can assign users to user groups based on theirinteractions with user interfaces provided by the account managementsystem 210. For example, the user group engine 235 may assign the usersto user groups based on similarities between their user profiles. A usergroup can include, as members of the user group, users that have atleast a threshold similarity with each other user in the group based ontheir user profiles. For example, a similarity score can be determinedfor each pair of users based on a similarity between data stored in thetwo users' profiles. If the similarity score satisfies a threshold(e.g., by meeting or exceeding the threshold), the two users may beincluded in a user group together. The similarity score can be based ona number of matching characteristics between the two users. For example,if the two users have requested the same types of data and/or selectedthe same user interface elements, the two users may have a highersimilarity score than if the two users have not requested the same typesof data or have not selected the same user interface elements. The usergroups can be used to identify account data and user interface elementsto provide to members of the groups as described in more detail below.

In some implementations, the user groups are based on particular rolesin organizations. For example, the user group engine 235 may create andpopulate a user group for product managers and another user group foraccountants. A user group for a particular role can include users thathave a user profile that matches or is similar to a profile for theparticular role. For example, users in particular roles may access thesimilar types of data over similar data dimensions and/or view the sameor similar user interface elements.

A user group can include users for multiple different account holders.For example, the user group for product managers may include productmanagers for multiple different organizations. In this way, patterns ofuser interactions from multiple different organizations can be used toidentify types of data that are more likely to be requested by usershaving the same roles or that are otherwise similar. An example processfor assigning users to user groups is illustrated in FIG. 6 anddescribed below.

As mentioned above, the data selector 221 can select data to provide toa user based on the user's previous interactions with user interfacesprovided by the account management system 210. In particular, the dataselector 221 may select data to provide in an initial account view forthe user based on the user's previous interactions with user interfacesprovided by the account management system 210. For example, when theuser accesses an account at the account management system 210, the dataselector 221 may select a first dataset of account data to provide in aninitial account view for the user in response to the user accessing theaccount, and potentially data to be cached by the client device eventhough that data may not be used for the initial account view.

The data selector 221 may select data for inclusion in the first datasetbased on a frequency at which particular data is requested or viewed bythe user, a frequency at which particular types of data are requested orviewed by the user, a frequency at which the user has interacted withparticular user interface elements, and/or other data included in theuser's profile. For example, the initial account view may include aparticular number of cards, e.g., selected by the user interfacegenerator 229. The data selector 221 can select a first dataset forpopulating the display cards. This first dataset may include the mostfrequently requested data and/or the most frequently selected types ofdata for inclusion in the display cards.

The data selector 221 may select the first dataset based on the datadimensions requested by the user. For example, the first dataset mayinclude data for a particular time period for which the user haspreviously requested data. In a particular example, a user may only beinterested in recent data, e.g., data for events that occurred in thelast week. In this example, the user may often request data for theprevious week without requesting older data. The data selector 221 mayprovide this user, for presentation in an initial account view, a firstdataset that includes data regarding events that occurred in the weekprior to the user logging in. The data selector 221 may determine to notprovide older data to this user until the user requests the data,resulting in less data being provided over the network and stored at theclient device.

The data dimensions used in selecting the first dataset may also beselected based on frequency. For example, a user may request data fordifferent time periods or different geographic locations. The dataselector 221 may select the first dataset based on the most frequentlyrequested time period(s) or geographic location(s).

The data selector 221 may select the first dataset for the initialaccount view based on the types of data to be presented in the initialaccount view for the user. For example, a particular display card maypresent a particular type of data. If the particular card is selectedfor the initial account view, then the data selector 221 may select, forinclusion in the first dataset, the appropriate data for populating theparticular display card.

In some implementations, the data selector 221 can also select the firstdataset based on a user group or role to which the user has beenassigned. For example, other users in the group or that have the samerole may request particular types of data or interact with particularuser interface elements (e.g., particular display cards). The dataselector 221 may include types of data requested by other users in thegroup (or that are assigned the same role) in the first dataset as theuser may be interested in these types of data or may find these types ofdata useful. Of course, the actual data from other accounts would not beincluded in the first dataset. Instead, the data selector 221 mayidentify, within the account that the user is authorized to access,account data of the same type that other users in the group haverequested.

The data selector 221 can select for inclusion in the first dataset thetypes of data requested by others in the user group based on thefrequency at which other users in the group request or view the types ofdata. For example, if the group as a whole most frequently requests orviews a particular type of data, data of that particular type may beincluded in the first dataset. The data selector 221 can also select forinclusion in the first dataset the types of data requested by otherusers in the user group based on the number of other users that requestor view the types of data. For example, a particular type of data thatis requested or viewed by the most users (or at least a threshold numberof users) may be included in the first dataset.

Similarly, the user interface generator 229 can select user interfaceelements, e.g., display cards, to include in the initial account viewbased on the user interface elements that other users in the user grouphave selected or viewed. For example, the user interface generator 229may select user interface elements for the initial account view based onthe number of times users in the user group have selected or viewed theuser interface elements and/or the number of users in the group thathave selected or viewed the user interface elements.

By selecting user interface elements and data to include in the initialaccount view for a user based on the user's previous interactions withuser interfaces provided by the account management system 210 and/orbased on the interactions of other users included in a group with theuser, the account management system 210 can provide a summary of datathat is likely to be the most useful to the user, thereby improving theusefulness of the summary of data. This can result in greater usersatisfaction and a reduction in the number of requests for additionaldata submitted by the user. Thus, this selection process can reduce thedemand placed on a network and the latency caused by the network.

The data selector 221 includes a pre-caching engine 223 and a campaigngrouper 225. The pre-caching engine 223 can select one or more seconddatasets to provide to a client device in response to a request foraccount data. The pre-caching engine 223 can select the second datasetin response to specific requests for specific data and/or general orimplicit requests for data (e.g., user logging into account). Thepre-caching engine 223 can select and provide the second dataset priorto receiving a request for the data included in the second dataset. Forexample, the second dataset can be data that was not specified in aspecific request or that was not selected for inclusion in the firstdataset provided for the initial account view.

The pre-caching engine 223 can send the second dataset to the clientdevice with account data obtained in response to a specific request orwith the first dataset. Or, the pre-caching engine 223 can provide thesecond dataset after the other data has been sent to the client device.The client device can store the second dataset in a high-speed cache264. In this way, the account data of the second dataset can bepresented to the user more quickly in the event that the user requestssuch data.

The pre-caching engine 223 can select data for inclusion in the seconddataset for a user based on the user's previous interactions with userinterfaces provided by the account management system 210 and/or the usergroup or role to which the user has been assigned. Similar criteria usedto select the first dataset can be used to select the second dataset.For example, the pre-caching engine 223 can select data for inclusion inthe second dataset based on a frequency at which particular data isrequested or viewed by the user, a frequency at which particular typesof data are requested or viewed by the user, a frequency at which theuser has interacted with particular user interface elements, the datadimensions requested by the user, the frequency at which other users inthe user group request or view types of data, the number of other usersin the user group that request or view the types of data, and/or otherappropriate data regarding the user's interaction with user interfacesand data regarding other users' interactions with user interfaces.

In some implementations, the first dataset may be selected based on theuser's previous interactions with the user interfaces while the seconddataset is selected based on interactions of other users in the usergroup or role to which the user has been assigned. In someimplementations, the first dataset and the second dataset are bothselected based on a combination of the user's previous interactions withuser interfaces provided by the account management system 210 and theinteractions of other users in the user group or role to which the userhas been assigned. In this example, the user's interactions may be givenmore weight than the interactions of other users in the user group orrole to which the user has been assigned.

In some implementations, the pre-caching engine 223 may store the seconddataset, a portion of the second dataset, or a different third datasetin a high-speed cache 245 of the front-end server(s) 240. For example,the front-end server(s) 240 may include or be coupled to a high-speedcache 245 that includes high-speed memory, such as SRAM and/or solidstate memory devices. In some implementations, the second dataset may bestored in the high-speed cache 245 of the account management system 210rather than in the high-speed cache of the client device. In someimplementations, a portion of the second dataset is stored in thehigh-speed cache 245 of the account management system 210 and a portionof the second dataset is cached at the client device.

In some implementations, the second dataset may be stored in thehigh-speed cache of the client device and a third dataset may be storedin the high-speed cache 245 of the account management system 210. Thethird dataset may be selected in a similar manner as the second dataset.By storing additional data at the front-end server(s), the latency inpresenting the additional data in response to a request for theadditional data can be reduced as it eliminates the time required toidentify and retrieve the data from the account data storage device 227.

The campaign grouper 225 can identify groups of campaigns (or othergroups of information) that are similar, but have a particularcharacteristic in which all of the campaigns differ. For example, anaccount holder may have multiple different campaigns for the sameproduct or service and that uses the same keywords and content items.However, each campaign may be directed to a different state. In thisexample, the content item distribution criteria may be the same for eachcampaign except the state in which the content item for each campaigncan be distributed. The campaign grouper 225 can identify and add thesecampaigns to a campaign group.

The user interface generator 229 can generate a visualization for eachcampaign group that highlights the difference between the campaigns andany difference in campaign performance based on the difference.Continuing the previous example, the user interface generator 229 maygenerate a visualization that includes a map of the fifty states. On themap, the visualization may highlight the performance of the campaign ineach state, e.g., using performance numbers, colors that illustrate theperformance, or another visual effect that highlights the differencebetween the campaigns in the different states.

In another example, the user interface generator 229 may generate avisualization that highlights the differences in performance of the sameor similar campaigns that differ based on the day of the week in whichcontent items are provided for the campaigns. For example, a heat mapmay be used to show the relative performance of the campaign ondifferent days of the week. In yet another example, multiple campaignsmay differ only based on the type of keyword matching (e.g., exactmatch, broad match, etc.). In this example, a user interface may presentthe performance of the campaigns for each type of keyword matching.

FIG. 3 is a screenshot 300 of an example user interface 310 in whichaccount data is presented. The example user interface 310 includes aninitial account view of an account displayed in a dashboard for theaccount. The initial account view can be generated for a given user, forexample, based on the given user's interactions with user interfacesduring previous user sessions in which the user accessed the account.

The user interface 310 includes a menu 320 and a set of display cards330. The menu 310 can provide a list of other display cards that theuser can select to view. The menu 310 can also provide a list of datathat the user can select to view. In response to a selection of an itemin the menu 320, the user interface 310 can cause the client devicepresenting the user interface 310 to request the selected display cardor selected data. For example, the client device may first access acache of the client device to determine whether the selected data (ordata that is to be presented in the selected display card) is stored inthe cache. If so, the client device can obtain the data from the cacheand present the data in the user interface 310. If the data is notstored in the cache, the client device can request the data from aremote system e.g., the account management system 210 of FIG. 2.

Each display card can present a particular type of data in a particularmanner. For example, a display card 331 presents performance data (e.g.,number of conversions, number of clicks, and number of impressions) andcost data for a campaign. The display card 331 presents this data innumerical format and also includes a line chart that presents at least aportion of the performance and/or cost data.

A display card 333 presents performance and cost data for severaladvertising campaigns in a table format. Similarly, a display card 337presents in a table format performance and cost data for severalkeywords that have been used to distribute content items. Anotherdisplay card 335 presents bar graphs that illustrate performance andcost data for different types of devices at which content items for acampaign have been presented. Yet another display card 339 presents aheat map that illustrates a campaign metric (e.g., a performancemeasure, cost measure, etc.) over time. For example, the darkness ofeach square in the heat map may vary based on the value of the metricfor the corresponding time. The time range for the heat map can beadjusted by selecting “Day”, “Day & Hour”, or “Hour” at the top of thedisplay card 339.

As discussed above, the display cards and/or the data included in theinitial account view can be selected based on the user's previousinteractions with user interfaces and/or a user group to which the userhas been assigned. For example, the display cards 331-339 and the datapresented by the display cards 331-339 may be selected based on the userselecting the display cards 331-339 during a previous user session withthe account. In addition, the campaigns included in the display card 333may be selected based on the user previously requesting data related tothese campaigns. Similarly, the keywords included in the display card337 may be selected based on the user requesting data related to thesekeywords. In another example, the time range presented in the displaycard 339 may be selected based on the user previously interacting withthe display card 339 (or another display card) to view data for thattime period.

Additional cards with additional data can be provided to the clientdevice and cached at the client device prior to the user requesting theadditional cards. For example, the user interface 310 includes fivedisplay cards 331-339. However, the user may often view nine differentdisplay cards. The five display cards presented in the user interfaceand the other four display cards (along with the data presented in thedisplay cards) can be provided to the client device when the user logsinto the account. In this way, when the user selects one of the fourdisplay cards, the selected display card can be presented to the userquickly and without submitting another request over the network.

Another example display card can show the ways in which a particularcontent item has been displayed at user's devices. For example, acontent item may be presented in different ways based on the type ofclient device at which the content item is presented (e.g., a contentitem may be presented differently on a smartphone than a desktopcomputer), the location on a resource with which the content item ispresented (e.g., a content item may be presented differently at the topof a web page than on one side of a web page), or the type of resourcewith which the content item has been presented (e.g., a content item maybe presented differently on a search results page than on a blog). Forthis display card, the user interface generator 229 can make aprobabilistic determination as to how the content item was displayed foreach impression of the content item and display a representation of howthe content item was presented. For example, the user interfacegenerator 229 may make the probabilistic determination for a particularimpression based on the type of device at which the content item waspresented, the location on the resource at which the content item waspresented, the type of resource with which the content item waspresented, and/or other appropriate data that can affect thepresentation of a content item.

The display card can present a subset of the ways in which the contentitem was determined to have been presented. For example, the userinterface generator 229 may make a probabilistic determination as to howthe content item was displayed for each impression of the content item.The user interface generator 229 may count the number of impressions foreach way in which the content item may have been presented based on theprobabilistic determinations. The user interface generator 229 may thengenerate the display card that depicts the representation of the contentitem for the ways that have the most impressions. For example, the topfour representations based on impressions may be presented in thedisplay card. In this way, a user can quickly see how the content itemis likely to have been presented to users.

FIG. 4 is a flow chart of an example process 400 for reducing latency inpresenting account data. Operations of the process 400 can beimplemented, for example, by a data processing apparatus, such as theaccount management system 210 of FIG. 1. The process 400 can also beimplemented by instructions stored on computer storage medium, whereexecution of the instructions by a data processing apparatus cause thedata processing apparatus to perform the operations of the process 400.

A given user is authenticated for an online account (402). The onlineaccount may be an advertising account to which the user has access. Forexample, the user may be an employee of an organization for which anaccount management system manages the organization's account data.Multiple different users may have access to the account. For example,the organization may have different employees in different roles (e.g.,product manager, brand manager, campaign manager, etc.) that each haveaccess to the online account to view and/or modify data relevant to theemployees.

The given user may be authenticated based on data submitted through aclient device of the given user. For example, the user may provide aunique username and password to access the online account. The user maybe authenticated for the online account if the username and passwordprovided by the given user matches the username and password stored forthe given user.

A user session is initiated for the given user in response toauthenticating the user (404). The user session allows the user to viewaccount data for the online account. The account data can be presentedto the user using one or more user interfaces. For example, a dashboardmay be presented to the user. This dashboard can include an initialaccount view with an overview of the account. In addition, the dashboardmay include links or other user interface controls that enable the userto request additional data or select other display cards in which thegiven user may be interested.

A user group to which the given user is assigned is identified (406).For example, the given user may be assigned to one or more user groupsbased on similarities between the given user's interactions with userinterface elements presented in the user interface of the account duringprevious user sessions and other interactions of other users with theuser interface elements. The given user may also be assigned to a usergroup based on similarities between at least one type of data requestedby the given user during the previous user sessions and at least onetype of data requested by other users. An example process for assigningusers to user groups is illustrated in FIG. 6 and described below.

A first dataset related to the online account is selected (408). Thefirst dataset includes account data of the online account to which theuser have been authenticated to access. For example, the first datasetmay include account data for presentation in an initial account viewthat provides an overview of the online account to the given user. Theinitial account view may be custom to the given user and based on theuser's previous requests for and/or interactions with user interfaceelements (e.g., particular display cards, controls, graphs, etc.), thegiven user's requests or modifications to data or types of data, thegiven user's requests or views of particular dimensions of data (e.g.,time periods, geographic locations, etc.), how often the given useraccesses the online account, preferences selected by the given user, theuser group to which the given user has been assigned, and/or otherappropriate data. The initial account view can present multipledifferent types of data combined into a single presentation and thatprovides an overview of the online account to the given user.

In some implementations, the first dataset for presentation in theinitial account view may be selected from a data store of account datafor the online account based on the user's previous interactions withuser interfaces presented in previous user sessions of the given userand/or the user group(s) to which the given user has been assigned. Forexample, the first dataset may be selected based on the types of datarequested by the given user during the previous user sessions and/oruser interface elements with which the given user has interacted duringprevious user sessions of the given user. The first dataset may also beselected based on the types of data requested by the other user in theuser group(s) to which the given user has been assigned and/or userinterface elements with which the other users have interacted.

A second dataset related to the online account is selected (410). Thesecond dataset can include data that is not presented in the initialaccount view. Instead, the second dataset may be sent to the givenuser's client device for caching at the client device. In this way, ifthe given user requests to view additional data not shown in the initialaccount view, but that is included in the second dataset, the additionaldata can be presented to the given user without requesting theadditional data from a remote device. Thus, the latency in presentingthe additional data can be reduced.

In general the second dataset may include data that is likely to berelevant to the given user, but may not be as relevant as the data inthe first dataset. The second dataset can also be selected based on theuser's previous interactions with user interfaces presented in previoususer sessions of the given user and/or the user group(s) to which thegiven user has been assigned. For example, the second dataset may bedata that has been requested by at least a threshold number of otherusers in the user group(s) to which the given user has been assigned orthat has been requested at least a threshold number of times by otherusers in the user group(s).

A user interface for the account is updated to present at least aportion of the first dataset (412). For example, a user interface inwhich the given user submitted the authorization data can be updated topresent the initial account view of the account for the given user. Theinitial account view, which provides an overview of the online accountto the given user, can include at least a portion of the first dataset.

The latency in updating the user interface when presenting additionalportions of the first dataset or the second dataset at the client deviceis reduced by providing the second dataset to the client device prior toreceiving a request for the second dataset from the client device (414).For example, the second dataset can be sent to the client device withthe first dataset. In another example, the second dataset can be sent tothe client device after the first dataset is sent to the client device,but before a request for the second dataset is received. The seconddataset (and the first dataset) can be stored in a cache of the clientdevice to reduce the latency in presenting the cached data whenrequested at the client device.

After each user session, the given user's profile can be updated basedon the interactions of the given user with data and user interfaceelements during the user session. Based on the updates to the profile,the initial account view for the user may be updated. For example, theinitial account view may be updated to present a display card that theuser requested during the user session and/or data that the userrequested or modified during the user session. The included in the firstdataset and/or the second dataset may similarly be updated based onupdates to the given user's profile.

The cache of the client device may be refreshed with updated data, forexample, if the data has changed or the data has been stored in thecache for at least a threshold amount of time. However, there are costsassociated with updating the cache. For example, large amounts of datamay need to be obtained and transmitted across the network. Thus, apre-caching engine, e.g., the pre-caching engine 223 of FIG. 1, candetermine whether to update the cache based on these costs andassociated benefits with updating the cache.

FIG. 5 is a flow chart of an example process 500 for updating a cache.Operations of the process 500 can be implemented, for example, by a dataprocessing apparatus, such as the account management system 210 ofFIG. 1. The process 500 can also be implemented by instructions storedon computer storage medium, where execution of the instructions by adata processing apparatus cause the data processing apparatus to performthe operations of the process 500.

A trigger is identified for updating the cache of a client device (502).In some implementations, the trigger may be based on an amount of timethat has elapsed since data was transmitted to the client device forstorage in the cache. The trigger can also be based on whether datastored in the cache has changed from the value stored in the cache. Forexample, the number of conversions for a content item may have increaseddue to a new conversion event that occurred after the cache waspopulated with data that includes the number of conversions for thecontent item. The trigger can be based on a number of data items thathave changed since the data was transmitted to the client device forstorage in the cache. For example, if at least a threshold number ofdata items have changed, a cache update may be triggered. The triggercan also be based on a user modification to account data.

A determination is made whether to update the cache in response toidentifying the trigger (504). The determination can be based on a costassociated with updating the cache and a benefit associated withupdating the cache. For example, an update to the cache requires the useof computing resources and network resources to obtain updated data andtransmit the updated data to the client device. Another cost is theamount of time it takes to update the cache with the updated data.

The benefits include presenting up to date data rather than old data.The benefits may also include reduced latency in presenting the updateddata, for example, if the client device requests the updated data inresponse to a user request to view the data. However, the benefit of upto date data to a user may depend on the type of data. For example,impression data for a previous year is unlikely to change and any changewould likely be minimal. Thus, the benefit of updating a cache with datafor a historical time period may have little benefit. However, thebenefits of updating the current day's performance data may be verybeneficial to a user.

In some implementations, the determination of whether to update thecache is based on the type of data and/or the amount of data stored inthe cache. For example, some types of data can take longer to obtain andprovide over the network and/or include more data that has to betransmitted. In some implementations, the determination of whether toupdate the cache is based on historical data related to the types ofdata and/or amount of data stored in the cache. For example, thedetermination may be based on an analysis of previous latency numbersfor previous query patterns.

If a determination is made to not update the cache, the cache is notupdated. Instead, the process 500 may wait until another trigger isidentified and another determination can be made at that time whether toupdate the cache. If a determination to update the cache is made,updated data is obtained for at least a portion of the data stored inthe cache (506). For example, all of the cached data may be updated. Inanother example, only the data that has been changed since the data wascached at the client device may be updated.

The updated data is transmitted to the client device (508). For example,the updated data may be transmitted to the client device over a networkusing one or more data transmissions of one or more data packets. Oncereceived, the client device can replace the previous cached data withthe updated data.

FIG. 6 is a flow chart of an example process 600 for assigning a givenuser to a user group and identifying data to provide to the given userbased on the user group. Operations of the process 600 can beimplemented, for example, by a data processing apparatus, such as theaccount management system 210 of FIG. 1. The process 600 can also beimplemented by instructions stored on computer storage medium, whereexecution of the instructions by a data processing apparatus cause thedata processing apparatus to perform the operations of the process 600.

A user profile is obtained for a given user (602). The user profile forthe given user can include data describing pervious user interactionswith user interfaces that present account data. For example, asdescribed above, the user profile for a given user may include dataidentifying each user interface element with which the given user hasinteracted, the number of times the given user has interacted with theuser interface element, and/or the frequency with which the given userhas interacted with the user interface element. The user profile for agiven user may also include data identifying each type of data requestedby or modified by the given user, a number of times the given user hasrequested or modified each type of data, and a frequency with which thegiven user requests or modifies each type of data. The same identifyingand frequency data can be stored for each particular portion of actualdata requested or modified by the given user. For each type of dataand/or for each particular portion of data requested by the given user,the user profile can include the dimensions for the data (e.g., timeperiod or geographic location for the data).

The given user is assigned to a user group based on the user profile forthe given user (604). In some implementations, the given user isassigned to a user group based on a similarity between the given user'sprofile and other users' user profiles. For example, the given user maybe assigned to a user group with other users that have similar userprofiles. In particular, the given user may be assigned to a user groupbased on similarities between the given user's interactions with userinterface elements (e.g., controls) presented in user interface for theuser's account during previous user sessions and other interactions ofother users with user interface elements presented in user interfaces.The given user may also be assigned to a user group based on asimilarity between types of data requested by the given user and typesof data requested by other users and/or the similarity betweendimensions of data requested by the given user and other users.

In some implementations, a machine learning process is used to generateand populate user groups based on similarities between the user profilesof the users. For example, the machine learning process may be based ondecision trees, neural networks, deep learning, and/or clusteringtechniques.

Types of data and user interface elements are identified for the givenuser based on the user group(s) to which the given user is assigned. Forexample, the given user may be provided types of data requested by otherusers in the group and/or user interface elements selected or viewed byother users in the group. In a particular example, the given user may beprovided types of data requested by at least a threshold number of usersin the user group or the types of data requested most frequently byusers in the user group. Similarly, the given user may be provided userinterface elements selected or viewed by at least a threshold number ofusers in the group and/or user interface elements most frequentlyselected or viewed by users in the user group.

FIG. 7 is a flow chart of an example process 700 for generating avisualization that presents account data for multiple campaigns.Operations of the process 700 can be implemented, for example, by a dataprocessing apparatus, such as the account management system 210 ofFIG. 1. The process 700 can also be implemented by instructions storedon computer storage medium, where execution of the instructions by adata processing apparatus cause the data processing apparatus to performthe operations of the process 700.

Multiple campaigns of an account holder are identified (702). Forexample, an account holder may have multiple different advertisingcampaigns. In a particular example, an account holder may have multipledifferent campaigns for a product or service. The account holder mayalso have campaigns for other products or services.

A set of similar campaigns of the account holder is identified (704).The set of similar campaigns can include campaigns that are similar, buthave a particular characteristic in which all of the campaigns differ.For example, the account holder may have multiple different campaignsfor a particular product and with the same distribution criteria, butwith a different content item that is distributed for each campaign.These different campaigns can be included in a set of campaigns for theparticular product.

A visualization is generated for the set of campaigns (706). Forexample, the visualization may highlight the difference in data for thecampaigns in the set of campaigns. Continuing the previous example, thevisualization may highlight the performance of each content item foreach campaign in the set of campaigns. The visualization can beautomatically generated and provided in a display card for presentationat a client device of the account holder's user(s). For example, thevisualization may be automatically generated in response to identifyingthe set of similar campaigns and in such a way that it highlights theone different characteristic.

Further to the descriptions above, a user may be provided with controlsallowing the user to make an election as to both if and when systems,programs or features described herein may enable collection of userinformation (e.g., information about a user's social network, socialactions or activities, profession, a user's preferences, or a user'scurrent location), and if the user is sent content or communicationsfrom a server. In addition, certain data may be treated in one or moreways before it is stored or used, so that personally identifiableinformation is removed. For example, a user's identity may be treated sothat no personally identifiable information can be determined for theuser, or a user's geographic location may be generalized where locationinformation is obtained (such as to a city, ZIP code, or state level),so that a particular location of a user cannot be determined. Thus, theuser may have control over what information is collected about the user,how that information is used, and what information is provided to theuser.

Embodiments of the subject matter and the operations described in thisspecification can be implemented in digital electronic circuitry, or incomputer software, firmware, or hardware, including the structuresdisclosed in this specification and their structural equivalents, or incombinations of one or more of them. Embodiments of the subject matterdescribed in this specification can be implemented as one or morecomputer programs, i.e., one or more modules of computer programinstructions, encoded on computer storage medium for execution by, or tocontrol the operation of, data processing apparatus. Alternatively or inaddition, the program instructions can be encoded on anartificially-generated propagated signal, e.g., a machine-generatedelectrical, optical, or electromagnetic signal, that is generated toencode information for transmission to suitable receiver apparatus forexecution by a data processing apparatus. A computer storage medium canbe, or be included in, a computer-readable storage device, acomputer-readable storage substrate, a random or serial access memoryarray or device, or a combination of one or more of them. Moreover,while a computer storage medium is not a propagated signal, a computerstorage medium can be a source or destination of computer programinstructions encoded in an artificially-generated propagated signal. Thecomputer storage medium can also be, or be included in, one or moreseparate physical components or media (e.g., multiple CDs, disks, orother storage devices).

The operations described in this specification can be implemented asoperations performed by a data processing apparatus on data stored onone or more computer-readable storage devices or received from othersources.

The term “data processing apparatus” encompasses all kinds of apparatus,devices, and machines for processing data, including by way of example aprogrammable processor, a computer, a system on a chip, or multipleones, or combinations, of the foregoing The apparatus can includespecial purpose logic circuitry, e.g., an FPGA (field programmable gatearray) or an ASIC (application-specific integrated circuit). Theapparatus can also include, in addition to hardware, code that createsan execution environment for the computer program in question, e.g.,code that constitutes processor firmware, a protocol stack, a databasemanagement system, an operating system, a cross-platform runtimeenvironment, a virtual machine, or a combination of one or more of them.The apparatus and execution environment can realize various differentcomputing model infrastructures, such as web services, distributedcomputing and grid computing infrastructures.

A computer program (also known as a program, software, softwareapplication, script, or code) can be written in any form of programminglanguage, including compiled or interpreted languages, declarative orprocedural languages, and it can be deployed in any form, including as astand-alone program or as a module, component, subroutine, object, orother unit suitable for use in a computing environment. A computerprogram may, but need not, correspond to a file in a file system. Aprogram can be stored in a portion of a file that holds other programsor data (e.g., one or more scripts stored in a markup languagedocument), in a single file dedicated to the program in question, or inmultiple coordinated files (e.g., files that store one or more modules,sub-programs, or portions of code). A computer program can be deployedto be executed on one computer or on multiple computers that are locatedat one site or distributed across multiple sites and interconnected by acommunication network.

The processes and logic flows described in this specification can beperformed by one or more programmable processors executing one or morecomputer programs to perform actions by operating on input data andgenerating output. The processes and logic flows can also be performedby, and apparatus can also be implemented as, special purpose logiccircuitry, e.g., an FPGA (field programmable gate array) or an ASIC(application-specific integrated circuit).

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andany one or more processors of any kind of digital computer. Generally, aprocessor will receive instructions and data from a read-only memory ora random access memory or both. The essential elements of a computer area processor for performing actions in accordance with instructions andone or more memory devices for storing instructions and data. Generally,a computer will also include, or be operatively coupled to receive datafrom or transfer data to, or both, one or more mass storage devices forstoring data, e.g., magnetic, magneto-optical disks, or optical disks.However, a computer need not have such devices. Moreover, a computer canbe embedded in another device, e.g., a mobile telephone, a personaldigital assistant (PDA), a mobile audio or video player, a game console,a Global Positioning System (GPS) receiver, or a portable storage device(e.g., a universal serial bus (USB) flash drive), to name just a few.Devices suitable for storing computer program instructions and datainclude all forms of non-volatile memory, media and memory devices,including by way of example semiconductor memory devices, e.g., EPROM,EEPROM, and flash memory devices; magnetic disks, e.g., internal harddisks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROMdisks. The processor and the memory can be supplemented by, orincorporated in, special purpose logic circuitry.

To provide for interaction with a user, embodiments of the subjectmatter described in this specification can be implemented on a computerhaving a display device, e.g., a CRT (cathode ray tube) or LCD (liquidcrystal display) monitor, for displaying information to the user and akeyboard and a pointing device, e.g., a mouse or a trackball, by whichthe user can provide input to the computer. Other kinds of devices canbe used to provide for interaction with a user as well; for example,feedback provided to the user can be any form of sensory feedback, e.g.,visual feedback, auditory feedback, or tactile feedback; and input fromthe user can be received in any form, including acoustic, speech, ortactile input. In addition, a computer can interact with a user bysending documents to and receiving documents from a device that is usedby the user; for example, by sending web pages to a web browser on auser's client device in response to requests received from the webbrowser.

Embodiments of the subject matter described in this specification can beimplemented in a computing system that includes a back-end component,e.g., as a data server, or that includes a middleware component, e.g.,an application server, or that includes a front-end component, e.g., aclient computer having a graphical user interface or a Web browserthrough which a user can interact with an implementation of the subjectmatter described in this specification, or any combination of one ormore such back-end, middleware, or front-end components. The componentsof the system can be interconnected by any form or medium of digitaldata communication, e.g., a communication network. Examples ofcommunication networks include a local area network (“LAN”) and a widearea network (“WAN”), an inter-network (e.g., the Internet), andpeer-to-peer networks (e.g., ad hoc peer-to-peer networks).

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other. In someembodiments, a server transmits data (e.g., an HTML, page) to a clientdevice (e.g., for purposes of displaying data to and receiving userinput from a user interacting with the client device). Data generated atthe client device (e.g., a result of the user interaction) can bereceived from the client device at the server.

While this specification contains many specific implementation details,these should not be construed as limitations on the scope of anyinventions or of what may be claimed, but rather as descriptions offeatures specific to particular embodiments of particular inventions.Certain features that are described in this specification in the contextof separate embodiments can also be implemented in combination in asingle embodiment. Conversely, various features that are described inthe context of a single embodiment can also be implemented in multipleembodiments separately or in any suitable subcombination. Moreover,although features may be described above as acting in certaincombinations and even initially claimed as such, one or more featuresfrom a claimed combination can in some cases be excised from thecombination, and the claimed combination may be directed to asubcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the embodiments described above should not be understoodas requiring such separation in all embodiments, and it should beunderstood that the described program components and systems cangenerally be integrated together in a single software product orpackaged into multiple software products.

Thus, particular embodiments of the subject matter have been described.Other embodiments are within the scope of the following claims. In somecases, the actions recited in the claims can be performed in a differentorder and still achieve desirable results. In addition, the processesdepicted in the accompanying figures do not necessarily require theparticular order shown, or sequential order, to achieve desirableresults. In certain implementations, multitasking and parallelprocessing may be advantageous.

What is claimed is:
 1. A method performed by a data processingapparatus, the method comprising: generating, by the data processingapparatus and for presentation on a client device during a same usersession initiated by a particular user, a visualization of an initialdashboard user interface that includes multiple different display cardsthat provide different reports for a given online account forpresentation to the particular user during the same user session,wherein the multiple different display cards present different types ofdata in a same user interface; selecting, by the data processingapparatus, a set of data for a different display card that is notincluded in the initial dashboard user interface; and reducing latencyfor presenting an updated dashboard user interface at the client deviceduring the same user session in which the initial dashboard userinterface is displayed at the client device for presentation to theparticular user during the same user session by pre-caching, at theclient device, the set of data for the different display card that isnot included in the initial dashboard, wherein the pre-caching isperformed prior to a request from the client device to present thedifferent display card and while the initial dashboard user interface isdisplayed at the client device during the same user session; detecting,during the same user session, a trigger to update the pre-cached set ofdata for the different display card; determining, in response todetecting the trigger and during the same user session, whether toupdate the pre-cached set of data for the different display card,including: updating the pre-cached set of data for the different displaycard when an analysis indicates that the pre-cached set of data shouldbe updated; and waiting for another trigger before updating thepre-cached set of data for the different display card when the analysisindicates that the pre-cached set of data should not be updated; whereinthe trigger to update the pre-cached set of data for the differentdisplay card is based on an amount of time that has elapsed since datawas transmitted to the client device for storage in a cache of theclient device that is at least a threshold amount of time.
 2. The methodof claim 1, wherein the trigger to update the pre-cached set of data forthe different display card is based on a value of the data stored in acache on the client device that is a different value than a currentvalue of the data.
 3. The method of claim 2, wherein the trigger toupdate the pre-cached set of data for the different display card isbased on a threshold number of data items of the pre-cached set of datathat have changed from a previous update to the pre-cached set of datain the cache.
 4. The method of claim 1, wherein determining, whether toupdate the pre-cached set of data for the different display card isbased on i) a type of data stored in a cache on the client device, ii)an amount of data stored in the cache on the client device, or iii) acombination thereof.
 5. The method of claim 1, wherein updating thepre-cached set of data for the different display card includes replacingpreviously cached data with updated data.
 6. The method of claim 1,further comprising: after pre-caching the set of data for the differentdisplay card, receiving the request to present the different displaycard from the client device; and generating, by the data processingapparatus, a visualization of the updated dashboard user interface thatincludes the different display card that was not included in the initialdashboard user interface and that was pre-cached at the client deviceprior to the request by the particular user to present the differentdisplay card.
 7. A system, comprising: a first front-end server,including one or more processors, that generates, for presentation on aclient device during a same user session initiated by a particular user,a visualization of an initial dashboard user interface that includesmultiple different display cards that provide different reports for agiven online account for presentation to the particular user during thesame user session, wherein the multiple different display cards presentdifferent types of data in a same user interface; and a second front-endserver, including one or more processors, that selects a set of data fora different display card that is not included in the initial dashboarduser interface, reduces latency for presenting an updated dashboard userinterface at the client device during the same user session in which theinitial dashboard user interface is displayed at the client device forpresentation to the particular user during the same user session bypre-caching, at the client device, the set of data for the differentdisplay card that is not included in the initial dashboard, wherein thepre-caching is performed prior to a request from the client device topresent the different display card and while the initial dashboard userinterface is displayed at the client device during the same usersession, and detects, during the same user session, a trigger to updatethe pre-cached set of data for the different display card, determines,in response to detecting the trigger and during the same user session,whether to update the pre-cached set of data for the different displaycard, including: updating the pre-cached set of data for the differentdisplay card when an analysis indicates that the pre-cached set of datashould be updated; and waiting for another trigger before updating thepre-cached set of data for the different display card when the analysisindicates that the pre-cached set of data should not be updated; whereinthe trigger to update the pre-cached set of data for the differentdisplay card is based on an amount of time that has elapsed since datawas transmitted to the client device for storage in a cache of theclient device that is at least a threshold amount of time.
 8. The systemof claim 7, wherein the trigger to update the pre-cached set of data forthe different display card is based on a value of the data stored in acache on the client device that is a different value than a currentvalue of the data.
 9. The system of claim 8, wherein the trigger toupdate the pre-cached set of data for the different display card isbased on a threshold number of data items of the pre-cached set of datathat have changed from a previous update to the pre-cached set of datain the cache.
 10. The system of claim 7, wherein determining, whether toupdate the pre-cached set of data for the different display card isbased on i) a type of data stored in a cache on the client device, ii)an amount of data stored in the cache on the client device, or iii) acombination thereof.
 11. The system of claim 7, wherein updating thepre-cached set of data for the different display card includes replacingpreviously cached data with updated data.
 12. The system of claim 7,further comprising: after pre-caching the set of data for the differentdisplay card, receiving the request to present the different displaycard from the client device; and generating a visualization of theupdated dashboard user interface that includes the different displaycard that was not included in the initial dashboard user interface andthat was pre-cached at the client device prior to the request by theparticular user to present the different display card.
 13. Anon-transitory computer storage medium encoded with a computer program,the program comprising instructions that when executed by one or moredata processing apparatus cause the data processing apparatus to performoperations comprising: generating, by the data processing apparatus andfor presentation on a client device during a same user session initiatedby a particular user, a visualization of an initial dashboard userinterface that includes multiple different display cards that providedifferent reports for a given online account for presentation to theparticular user during the same user session, wherein the multipledifferent display cards present different types of data in a same userinterface; selecting, by the data processing apparatus, a set of datafor a different display card that is not included in the initialdashboard user interface; and reducing latency for presenting an updateddashboard user interface at the client device during the same usersession in which the initial dashboard user interface is displayed atthe client device for presentation to the particular user during thesame user session by pre-caching, at the client device, the set of datafor the different display card that is not included in the initialdashboard, wherein the pre-caching is performed prior to a request fromthe client device to present the different display card and while theinitial dashboard user interface is displayed at the client deviceduring the same user session; detecting, during the same user session, atrigger to update the pre-cached set of data for the different displaycard; determining, in response to detecting the trigger and during thesame user session, whether to update the pre-cached set of data for thedifferent display card, including: updating the pre-cached set of datafor the different display card when an analysis indicates that thepre-cached set of data should be updated; and waiting for anothertrigger before updating the pre-cached set of data for the differentdisplay card when the analysis indicates that the pre-cached set of datashould not be updated; wherein the trigger to update the pre-cached setof data for the different display card is based on an amount of timethat has elapsed since data was transmitted to the client device forstorage in a cache of the client device that is at least a thresholdamount of time.
 14. The storage medium of claim 13, wherein the triggerto update the pre-cached set of data for the different display card isbased on a value of the data stored in a cache on the client device thatis a different value than a current value of the data.
 15. The storagemedium of claim 14, wherein the trigger to update the pre-cached set ofdata for the different display card is based on a threshold number ofdata items of the pre-cached set of data that have changed from aprevious update to the pre-cached set of data in the cache.
 16. Thestorage medium of claim 13, wherein determining, whether to update thepre-cached set of data for the different display card is based on i) atype of data stored in a cache on the client device, ii) an amount ofdata stored in the cache on the client device, or iii) a combinationthereof.
 17. The storage medium of claim 13, further comprising: afterpre-caching the set of data for the different display card, receivingthe request to present the different display card from the clientdevice; and generating, by the data processing apparatus, avisualization of the updated dashboard user interface that includes thedifferent display card that was not included in the initial dashboarduser interface and that was pre-cached at the client device prior to therequest by the particular user to present the different display card.